Part Number Hot Search : 
FRL130D EM2710 AT27C800 LC8902Q SEL1210R GFP50N03 MS7M5 B1575
Product Description
Full Text Search
 

To Download MYXX28HC256 Datasheet File

  If you can't view the Datasheet, Please click here to try to view without PDF Reader .  
 
 


  Datasheet File OCR Text:
  MYXX28HC256 revision 1.4 - 02/13 1 256kb eeprom MYXX28HC256 features ? access time (ns): 70, 90, 120, 150 ? simple byte and page write ? single 5v supply ? no external high voltages or vpp control circuits ? self-timed ? no erase before write ? no complex programming algorithms ? no overerase problem ? low power cmos: ? active: 60ma ? standby: 500ma ? software data protection ? protects data against system level inadvertent writes ? high speed page write capability ? highly reliable direct write? cell ? endurance: 100,000 write cycles ? data retention: 100 years ? early end of write detection ? data polling ? toggle bit polling options markings timing 70 ns access 90 ns access 120 ns access 150 ns access -7 -9 -12 -15 packages ceramic ? at pack cerdip, 600 mil cerlcc cerpga cersoj f cw eca p ecj operating temp. military (-55c to +125c) industrial (-40c to +85c) xt it 32k x 8 eeprom - 5 volt, byte alterable description the MYXX28HC256 is a high performance cmos 32k x 8 e 2 prom. it is fabricated with a textured poly ? oating gate technology, providing a highly reliable 5 volt only nonvolatile memory. the MYXX28HC256 supports a 128-byte page write operation, effectively providing a 24ms/byte write cycle and enabling the entire memory to be typically rewritten in less than 0.8 seconds. the MYXX28HC256 also features data polling and toggle bit polling, two methods of providing early end of write detection. the MYXX28HC256 also supports the jedec standard software data protection feature for protecting against inadvertent writes during power-up and power-down. endurance for the MYXX28HC256 is speci? ed as a minimum 100,000 write cycles per byte and an inherent data retention of 100 years. cersoj or cerlcc cerpga i/o 1 i/o 2 i/o 3 i/o 5 i/o 6 i/o 0 a 0 v ss v cc i/o 4 i/o 7 a 1 a 2 ce a 10 a 3 a 4 oe a 11 a 5 a 12 a 8 a 9 a 14 a 6 a 7 a 13 we a 6 a 5 a 4 a 3 a 2 a 1 a 0 nc i/o 0 a 8 a 9 a 1 1 nc oe# a 10 ce# i/o 7 i/o 6 4 3 2 1 32 31 30 14 15 16 17 18 19 20 5 6 7 8 9 10 1 1 12 13 29 28 27 26 25 24 23 22 21 myx28c32k8 myx28c32k8 a 7 a 12 a 14 nc v cc we# a 13 i/o 1 i/o 2 v ss nc i/o 3 i/o 4 i/o 5 cerd i p or flat pack a14 a 12 a 7 a 6 a 5 a 4 a 3 a 2 a 1 a 0 i/o 0 i/o 1 i/o 2 v ss 1 2 3 4 5 6 7 8 9 10 1 1 12 13 14 28 27 26 25 24 23 22 21 20 19 18 17 16 15 v cc we# a 13 a 8 a 9 a 1 1 oe# a 10 ce# i/o 7 i/o 6 i/o 5 i/0 4 i/o 3 12 13 15 17 18 1 1 10 14 16 19 9 8 20 21 7 6 22 23 5 2 28 24 25 431 27 26 cersoj or cerlcc cerpga i/o 1 i/o 2 i/o 3 i/o 5 i/o 6 i/o 0 a 0 v ss v cc i/o 4 i/o 7 a 1 a 2 ce a 10 a 3 a 4 oe a 11 a 5 a 12 a 8 a 9 a 14 a 6 a 7 a 13 we a 6 a 5 a 4 a 3 a 2 a 1 a 0 nc i/o 0 a 8 a 9 a 1 1 nc oe# a 10 ce# i/o 7 i/o 6 4 3 2 1 32 31 30 14 15 16 17 18 19 20 5 6 7 8 9 10 1 1 12 13 29 28 27 26 25 24 23 22 21 myx28c32k8 myx28c32k8 a 7 a 12 a 14 nc v cc we# a 13 i/o 1 i/o 2 v ss nc i/o 3 i/o 4 i/o 5 cerd i p or flat pack a14 a 12 a 7 a 6 a 5 a 4 a 3 a 2 a 1 a 0 i/o 0 i/o 1 i/o 2 v ss 1 2 3 4 5 6 7 8 9 10 1 1 12 13 14 28 27 26 25 24 23 22 21 20 19 18 17 16 15 v cc we# a 13 a 8 a 9 a 1 1 oe# a 10 ce# i/o 7 i/o 6 i/o 5 i/0 4 i/o 3 12 13 15 17 18 1 1 10 14 16 19 9 8 20 21 7 6 22 23 5 2 28 24 25 431 27 26 figure 1 - pin con? guration cersoj or cerlcc cerpga i/o 1 i/o 2 i/o 3 i/o 5 i/o 6 i/o 0 a 0 v ss v cc i/o 4 i/o 7 a 1 a 2 ce a 10 a 3 a 4 oe a 11 a 5 a 12 a 8 a 9 a 14 a 6 a 7 a 13 we a 6 a 5 a 4 a 3 a 2 a 1 a 0 nc i/o 0 a 8 a 9 a 1 1 nc oe# a 10 ce# i/o 7 i/o 6 4 3 2 1 32 31 30 14 15 16 17 18 19 20 5 6 7 8 9 10 1 1 12 13 29 28 27 26 25 24 23 22 21 myx28c32k8 myx28c32k8 a 7 a 12 a 14 nc v cc we# a 13 i/o 1 i/o 2 v ss nc i/o 3 i/o 4 i/o 5 cerd i p or flat pack a14 a 12 a 7 a 6 a 5 a 4 a 3 a 2 a 1 a 0 i/o 0 i/o 1 i/o 2 v ss 1 2 3 4 5 6 7 8 9 10 1 1 12 13 14 28 27 26 25 24 23 22 21 20 19 18 17 16 15 v cc we# a 13 a 8 a 9 a 1 1 oe# a 10 ce# i/o 7 i/o 6 i/o 5 i/0 4 i/o 3 12 13 15 17 18 1 1 10 14 16 19 9 8 20 21 7 6 22 23 5 2 28 24 25 431 27 26
MYXX28HC256 revision 1.4 - 02/13 2 256kb eeprom MYXX28HC256 pin descriptions addresses (a0?a14) the address inputs select an 8-bit memory location during a read or write operation. chip enable (ce#) the chip enable input must be low to enable all read/write operations. when ce# is high, power consumption is reduced. output enable (oe#) the output enable input controls the data output buffers and is used to initiate read operations. data in/data out (i/o 0 ?i/o 7 ) data is written to or read from the MYXX28HC256 through the i/o pins. write enable (we#) the write enable input controls the writing of data to the MYXX28HC256. table 1 - pin names parameter symbol a 0 -a 14 address inputs i/o 0 -i/0 7 data input/output we# write enable ce# chip enable oe# output enable v cc +5v v ss ground nc no connect x buffers la tches and decoder i/o buffers and la tches y buffers la tches and decoder control logic and timing 256k-bit eeprom arra y i/o 0 ?i/o 7 da t a inputs/outputs ce# oe# v cc v ss a 0 ?a 14 address inputs we# c m y cm my cy cmy k functional diagram.pdf 1 11/19/2012 8:59:32 am figure 2 - functional diagram
MYXX28HC256 revision 1.4 - 02/13 3 256kb eeprom MYXX28HC256 device operation read read operations are initiated by both oe# and ce# low. the read operation is terminated by either ce# or oe# returning high. this two line control architecture eliminates bus contention in a system environment. the data bus will be in a high impedance state when either oe# or ce# is high. write write operations are initiated when both ce# and we# are low and oe# is high. the MYXX28HC256 supports both a ce# and we# controlled write cycle. that is, the address is latched by the falling edge of either ce# or we#, whichever occurs last. similarly, the data is latched internally by the rising edge of either ce# or we#, whichever occurs ? rst. a byte write operation, once initiated, will automatically continue to completion, typically within 3ms. page write operation the page write feature of the MYXX28HC256 allows the entire memory to be written in typically 0.8 seconds. page write allows up to one hundred twenty-eight bytes of data to be consecutively written to the MYXX28HC256 prior to the commencement of the internal programming cycle. the host can fetch data from another device within the system during a page write operation (change the source address), but the page address (a7 through a14) for each subsequent valid write cycle to the part during this operation must be the same as the initial page address. the page write mode can be initiated during any write operation. following the initial byte write cycle, the host can write an additional one to one hundred twentyseven bytes in the same manner as the ? rst byte was written. each successive byte load cycle, started by the we# high to low transition, must begin within 100ms of the falling edge of the preceding we#. if a subsequent we# high to low transition is not detected within 100ms, the internal automatic programming cycle will commence. there is no page write window limitation. effectively the page write window is in? nitely wide, so long as the host continues to access the device within the byte load cycle time of 100ms. write operation status bits the MYXX28HC256 provides the user two write operation status bits. these can be used to optimize a system write cycle time. the status bits are mapped onto the i/o bus as shown in figure 3. figure 3 - status bit assignment data polling (i/o 7 ) the MYXX28HC256 features data polling as a method to indicate to the host system that the byte write or page write cycle has completed. data polling allows a simple bit test operation to determine the status of the MYXX28HC256, eliminating additional interrupt inputs or external hardware. during the internal programming cycle, any attempt to read the last byte written will produce the complement of that data on i/o 7 (i.e. write data = 0xxx xxxx, read data = 1xxx xxxx). once the programming cycle is complete, i/o 7 will re? ect true data. toggle bit (i/o 6 ) the MYXX28HC256 also provides another method for determining when the internal write cycle is complete. during the internal programming cycle i/o 6 will toggle from high to low and low to high on subsequent attempts to read the device. when the internal cycle is complete the toggling will cease and the device will be accessible for additional read and write operations. 5 tb dp 43210 i/o reser ved t oggle bit da t a polling c m y cm my cy cmy k status bit assignment.pdf 1 11/19/2012 10:02:12 am
MYXX28HC256 revision 1.4 - 02/13 4 256kb eeprom MYXX28HC256 data polling i/o 7 figure 4 - data polling bus sequence figure 5 - data polling software flow write data sa ve last data and address read last address io 7 comp are? MYXX28HC256 ready no yes writes complete? no yes ce# oe# we# i/o 7 MYXX28HC256 ready last write high z v ol v ih a 0 ?a 14 n a n a n a n a n a n a v oh an write data sa ve last data and address read last address io 7 comp are? MYXX28HC256 ready no yes writes complete? no yes ce# oe# we# i/o 7 MYXX28HC256 ready last write high z v ol v ih a 0 ?a 14 n a n a n a n a n a n a v oh an data polling can effectively halve the time for writing to the MYXX28HC256. the timing diagram in figure 4 illustrates the sequence of events on the bus. the software ? ow diagram in figure 5 illustrates one method of implementing the routine.
MYXX28HC256 revision 1.4 - 02/13 5 256kb eeprom MYXX28HC256 the toggle bit i/o 6 figure 6 - toggle bit bus sequence figure 7 - toggle bit software flow load accum from addr n comp are accum with addr n MYXX28HC256 ready comp are ok? no yes last write yes ce# oe# we# i/o 6 MYXX28HC256 ready v oh v ol last write high z * i/o 6 beginning and ending state of i/o 6 will vary . * * load accum from addr n comp are accum with addr n MYXX28HC256 ready comp are ok? no yes last write yes ce# oe# we# i/o 6 MYXX28HC256 ready v oh v ol last write high z * i/o 6 beginning and ending state of i/o 6 will vary . * * the toggle bit can eliminate the software housekeeping chore of saving and fetching the last address and data written to a device in order to implement data polling. this can be especially helpful in an array comprised of multiple MYXX28HC256 memories that is frequently updated. the timing diagram in figure 6 illustrates the sequence of events on the bus. the software ? ow diagram in figure 7 illustrates a method for polling the toggle bit.
MYXX28HC256 revision 1.4 - 02/13 6 256kb eeprom MYXX28HC256 hardware data protection the MYXX28HC256 provides two hardware features that protect nonvolatile data from inadvertent writes. ? default v cc sense - all write functions are inhibited when v cc is 3.5v typically. ? write inhibit - holding either oe# low, we# high, or ce# high will prevent an inadvertent write cycle during power-up and power-down, maintaining data integrity. software data protection the MYXX28HC256 offers a software controlled data protection feature. the MYXX28HC256 is shipped from micross with the software data protection not enabled; that is, the device will be in the standard operating mode. in this mode data should be protected during power-up/down operations through the use of external circuits. the host would then have open read and write access of the device once v cc was stable. the MYXX28HC256 can be automatically protected during power-up and power-down without the need for external circuits by employing the software data protection feature. the internal software data protection circuit is enabled after the ? rst write operation utilizing the software algorithm. this circuit is nonvolatile and will remain set for the life of the device unless the reset command is issued. once the software protection is enabled, the MYXX28HC256 is also protected from inadvertent and accidental writes in the powered-up state. that is, the software algorithm must be issued prior to writing additional data to the device. software algorithm selecting the software data protection mode requires the host system to precede data write operations by a series of three write operations to three speci? c addresses. refer to figure 9 and 10 for the sequence. the three-byte sequence opens the page write window enabling the host to write from one to one hundred twenty- eight bytes of data. once the page load cycle has been completed, the device will automatically be returned to the data protected state.
MYXX28HC256 revision 1.4 - 02/13 7 256kb eeprom MYXX28HC256 software data protection figure 8 - timing sequence - byte or page write figure 9 - write sequence for software data protection ce# we# (v cc ) write protected v cc 0v data address aa 5555 55 2aaa a0 5555 t blc max writes ok byte or p age t wc t blc max write last byte t o last address write da t a 55 t o address 2aaa write da t a a0 t o address 5555 write da t a xx t o any address after t wc re-enters da t a protected st a te write da t a aa t o address 5555 byte/p age load enabled optional byte or p age write allowed c m y cm my cy cmy k software data protection.pdf 1 11/19/2012 11:58:45 am ce# we# (v cc ) write protected v cc 0v data address aa 5555 55 2aaa a0 5555 t blc max writes ok byte or p age t wc t blc max write last byte t o last address write da t a 55 t o address 2aaa write da t a a0 t o address 5555 write da t a xx t o any address after t wc re-enters da t a protected st a te write da t a aa t o address 5555 byte/p age load enabled optional byte or p age write allowed c m y cm my cy cmy k software data protection.pdf 1 11/19/2012 11:58:45 am regardless of whether the device has previously been protected or not, once the software data protection algorithm is used and data has been written, the MYXX28HC256 will automatically disable further writes unless another command is issued to cancel it. if no further commands are issued the MYXX28HC256 will be write protected during power-down and after any subsequent power-up. note: once initiated, the sequence of write operations should not be interrupted.
MYXX28HC256 revision 1.4 - 02/13 8 256kb eeprom MYXX28HC256 resetting software data protection figure 10 - reset software data protection timing sequence figure 11 - write sequence for resetting software data protection ce# we# st andard opera ting mode v cc da t a address aa 5555 55 2aaa 80 5555 t wc aa 5555 55 2aaa 20 5555 write da t a 55 t o address 2aaa write da t a 55 t o address 2aaa write da t a 80 t o address 5555 write da t a aa t o address 5555 write da t a 20 t o address 5555 write da t a aa t o address 5555 after t wc , re-enters unprotected state c m y cm my cy cmy k resetting software data protection.pdf 1 11/19/2012 12:07:04 pm ce# we# st andard opera ting mode v cc da t a address aa 5555 55 2aaa 80 5555 t wc aa 5555 55 2aaa 20 5555 write da t a 55 t o address 2aaa write da t a 55 t o address 2aaa write da t a 80 t o address 5555 write da t a aa t o address 5555 write da t a 20 t o address 5555 write da t a aa t o address 5555 after t wc , re-enters unprotected state c m y cm my cy cmy k resetting software data protection.pdf 1 11/19/2012 12:07:04 pm in the event the user wants to deactivate the software data protection feature for testing or reprogramming in an eeprom programmer, the following six step algorithm will reset the internal protection circuit. after t wc , the MYXX28HC256 will be in standard operating mode. note: once initiated, the sequence of write operations should not be interrupted.
MYXX28HC256 revision 1.4 - 02/13 9 256kb eeprom MYXX28HC256 system considerations because the MYXX28HC256 is frequently used in large memory arrays it is provided with a two line control architecture for both read and write operations. proper usage can provide the lowest possible power dissipation and eliminate the possibility of contention where multiple i/o pins share the same bus. to gain the most bene? t it is recommended that ce# be decoded from the address bus and be used as the primary device selection input. both oe# and we# would then be common among all devices in the array. for a read operation this assures that all deselected devices are in their standby mode and that only the selected device(s) is outputting data on the bus. because the MYXX28HC256 has two power modes, standby and active, proper decoupling of the memory array is of prime concern. enabling ce# will cause transient current spikes. the magnitude of these spikes is dependent on the output capacitive loading of the l/os. therefore, the larger the array sharing a common bus, the larger the transient spikes. the voltage peaks associated with the current transients can be suppressed by the proper selection and placement of decoupling capacitors. as a minimum, it is recommended that a 0.1 f high frequency ceramic capacitor be used between v cc and v ss at each device. depending on the size of the array, the value of the capacitor may have to be larger. in addition, it is recommended that a 4.7 f electrolytic bulk capacitor be placed between v cc and v ss for each eight devices employed in the array. this bulk capacitor is employed to overcome the voltage droop caused by the inductive effects of the pc board traces.
MYXX28HC256 revision 1.4 - 02/13 10 256kb eeprom MYXX28HC256 table 2 - absolute maximum ratings* temperature under bias -10c to +85c -65c to +135c storage temperature -65c to +150c voltage on any pin with respect to v ss -1v to +7v dc output current 10ma lead temperature (soldering, 10 sec.) 300c supply voltage 5v 10% table 3 - recommended operating conditions temperature min. max. commerical 0c +70c industrial -40c +85c military -55c +125c *note stresses above those listed under absolute maximum ratings may cause permanent damage to the device. this is a stress rating only and the functional operation of the device at these or any other conditions above those indicated in the operational sections of this speci? cation is not implied. exposure to absolute maximum rating conditions for extended periods may affect device reliability. table 4 - dc operating characteristics over the recommended operating conditions unless otherwise speci? ed. symbol parameter limits units test conditions min. typ. 1 max. i cc v cc active current (ttl inputs) 30 60 ma ce# = oe# = v il ; we# = v ih all i/os = open; address inputs = .4v/2.4v levels @ f = 10mhz i sb1 v cc standby current (ttl inputs) 1 2 ce# = v ih ; oe# = v il ; all i/os = open; other inputs = v ih i sb2 v cc standby current (cmos inputs) 200 500 a ce# = v cc - 0.3v; oe# = gnd; all i/os = open; other inputs = v cc - 0.3v i li input leakage current 10 v in = v ss to v cc ; ce# = v ih i lo output leakage current 10 v out = v ss to v cc ; ce# = v ih v il 2 input low voltage -1 0.8 v v ih 2 input high voltage 2 v cc +1 v ol output low voltage 0.4 i ol = 6ma v oh output high voltage 2.4 i oh = -4ma 1. typical values are for t a = 25c and nominal supply voltage. 2. v il min. and v ih max. are for reference only and are not tested.
MYXX28HC256 revision 1.4 - 02/13 11 256kb eeprom MYXX28HC256 table 5 - power-up timing symbol parameter max. units t pur 1 power-up to read 100 s t puw 1 power-up to write 5 ms 1. this parameter is periodically sampled and not 100% tested. table 6 - capacitance t a = +25c; f = 1mhz; v cc = 5v symbol test max. units conditions c i/o input/output capacitance 10 pf v i/o = ov c in input capacitance 6 v in = ov table 7 - endurance and data retention parameter min. max. units endurance 100,000 cycles data retention 100 years table 8 - ac conditions of test input pulse levels 0v to 3v input rise and fall times 5ns input and output timing levels 1.5v table 9 - mode selection ce# oe# we# mode i/o power l l h read d out active h l write d in h x x standby & write inhibit high z standby x l x write inhibit x h
MYXX28HC256 revision 1.4 - 02/13 12 256kb eeprom MYXX28HC256 figure 12 - equivalent ac load circuit figure 13 - symbol table w a veform inputs outputs must be steady will be steady may change from low to high will change from low to high may change from high to low will change from high to low don?t care: changes allowed changing: state not known n/a center line is high impedance 5v 1.92k output 1.37k 30pf w a veform inputs outputs must be steady will be steady may change from low to high will change from low to high may change from high to low will change from high to low don?t care: changes allowed changing: state not known n/a center line is high impedance 5v 1.92k output 1.37k 30pf
MYXX28HC256 revision 1.4 - 02/13 13 256kb eeprom MYXX28HC256 ac characteristics over the recommended operating conditions unless otherwise speci? ed. table 10 - read cycle limits symbol parameter MYXX28HC256-70 MYXX28HC256-90 MYXX28HC256-12 MYXX28HC256-15 units min. max. min. max. min. max. min. max t rc read cycle time 70 90 120 150 ns t ce chip enable access time 70 90 120 150 t aa address access time t oe output enable access time 35 40 50 50 t lz 1 ce# low to output active 0 0 0 0 t olz 1 oe# low to output active t hz 1 ce# high to high z output 35 40 50 50 t ohz 1 oe# high to high z output t oh output hold from address change 0 0 0 0 1. t lz min., t hz , t olz min. and t ohz are periodically sampled and not 100% tested, t hz and t ohz are measured, with cl = 5pf, from the point when ce#, oe# return high (whichever occurs ? rst) to the time when the outputs are no longer driven. figure 14 - read cycle t ce t rc address ce# oe# we# da t a v alid da t a v alid t oe t lz t olz t oh t aa t hz t ohz data i/o v ih high z
MYXX28HC256 revision 1.4 - 02/13 14 256kb eeprom MYXX28HC256 table 11 - write cycle limits symbol parameter min. typ. 1 max. units t wc 2 write cycle time 3 5 ms t as address setup time 0 ns t ah address hold time 50 t cs write setup time 0 t ch write hold time 0 t cw ce# pulse width 50 t oes oe# high setup time 0 t oeh oe# high hold time 0 t wp we# pulse width 50 t wph 3 we# high recovery (page write only) 50 t dv data valid 1 s t ds data setup 50 ns t dh data hold 0 t dw 3 delay to next write after polling is true 10 s t blc byte load cycle 0.15 100 1. typical values are for t a = 25c and nominal supply voltage. 2. t wc is the minimum cycle time to be allowed from the system perspective unless pollin g techniques are used. it is the maximum time the device requires to automatically complete the inter nal write operation. 3. t wph and t dw are periodically sampled and not 100% tested. figure 15 - we# controlled write cycle address t as t wc t ah t oes t ds t dh t oeh ce# we# oe# data in data out high z t cs t ch t wp da t a v alid
MYXX28HC256 revision 1.4 - 02/13 15 256kb eeprom MYXX28HC256 figure 16 - ce# controlled write cycle figure 17 - page write cycle 1. between successive byte writes within a page write operation, oe# can be strobed low: e.g. this can be done with ce# and we# high to fetch data from another memory device within the system for the next write; or with we# high and ce# low effectively performing a polling operation. 2. the timings shown above are unique to page write operations. individual byte load operations within the page write must conform to either the ce# or we# controlled write cycle timing. address t as t oeh t wc t ah t oes t cs t ds t dh t ch ce# we# oe# da t a in data out high z t cw da t a v alid we# oe# 1 last byte byte 0 byte 1 byte 2 byte n byte n+1 byte n+2 t wp t wph t blc t wc ce# address 2 i/o *for each successive write within the page write operation, a 7 ?a 14 should be the same or writes to an unknown address could occur .
MYXX28HC256 revision 1.4 - 02/13 16 256kb eeprom MYXX28HC256 figure 18 - data polling diagram 1 figure 19 - toggle bit timing diagram 1 address a n d in =x d out =x d out =x t wc t oeh t oes a n a n ce# we# oe# i/o 7 t dw ce# oe# we# i/o 6 t oes t dw t wc t oeh high z * * *i/o 6 beginning and ending state will vary, depending upon actual t wc . 1. polling operations are by de? nition read cycles and are therefore subject to read cycle timings.
MYXX28HC256 revision 1.4 - 02/13 17 256kb eeprom MYXX28HC256 packaging information figure 20 - 28-lead hermetic dual in-line package type cw 0.020 (0.51) 0.016 (0.41) 0.150 (3.81) 0.125 (3.17) 0.610 (15.49) 0.590 (14.99) 0.1 10 (2.79) 0.090 (2.29) 1.460 (37.08) 1.400 (35.56) 1.300 (33.02) ref . pin 1 index 0.160 (4.06) 0.125 (3.17) 0.030 (0.76) 0.015 (0.38) pin 1 sea ting plane 0.062 (1.57) 0.050 (1.27) 0.550 (13.97) 0.510 (12.95) 0.085 (2.16) 0.040 (1.02) 0 15 note: all dimensions in inches (in p arentheses in millimeters) typ . 0.010 (0.25)
MYXX28HC256 revision 1.4 - 02/13 18 256kb eeprom MYXX28HC256 packaging information (continued) figure 21 - 32-pad ceramic leadless chip carrier package type eca 0.150 (3.81) bsc 0.300 (7.62) bsc 0.458 (1 1.63) ?? 0.458 (1 1.63) 0.442 (1 1.22) pin 1 0.400 (10.16) bsc 0.560 (14.22) 0.540 (13.71) 3926 fhd f14 0.020 (0.51) x 45 ref . 0.095 (2.41) 0.075 (1.91) 0.022 (0.56) 0.006 (0.15) 0.055 (1.39) 0.045 (1.14) typ . (4) plcs. 0.040 (1.02) x 45 ref . typ . (3) plcs. 0.050 (1.27) bsc 0.028 (0.71) 0.022 (0.56) (32) plcs. 0.200 (5.08) bsc 0.015 (0.38) 0.003 (0.08) 0.558 (14.17) ?? 0.088 (2.24) 0.050 (1.27) 0.120 (3.05) 0.060 (1.52) pin 1 index corder 1 32 note: 1. all dimensions in inches (in p arentheses in millimeters) 2. t olerance: 1% ntl 0.005 (0.127) 3926 fhd f14
MYXX28HC256 revision 1.4 - 02/13 19 256kb eeprom MYXX28HC256 packaging information (continued) figure 22 - 28-lead ceramic pin grid array package type p 0.561 (14.25) 0.541 (13.75) note: all dimensions in inches (in p arentheses in millimeters) 0.020 0.016 12 13 15 17 18 1 1 10 14 16 19 9 8 20 21 7 6 22 23 5 2 28 24 25 431 27 26 typ . 0.100 all leads 0.080 0.070 4 corners pin 1 index 0.660 (16.76) 0.640 (16.26) 0.100 0.080 0.072 0.061 0.185 (4.70) 0.175 (4.44) 0.050 0.008 a a a a note: leads 4,12,18 & 26 0.080 0.070
MYXX28HC256 revision 1.4 - 02/13 20 256kb eeprom MYXX28HC256 packaging information (continued) figure 23 - 28-lead ceramic flat pack type f note: all dimensions in inches (in p arentheses in millimeters) 0.740 (18.80) max. 0.019 (0.48) 0.015 (0.38) 0.050 (1.27) bsc 0.045 (1.14) max. pin 1 index 8 2 1 0.130 (3.30) 0.090 (2.29) 0.045 (1.14) 0.025 (0.66) 0.180 (4.57) min. 0.006 (0.15) 0.003 (0.08) 0.030 (0.76) min. 0.370 (9.40) 0.250 (6.35) typ . 0.300 2 plcs. 0.440 (1 1.18) max.
MYXX28HC256 revision 1.4 - 02/13 21 256kb eeprom MYXX28HC256 packaging information (continued) figure 24 - 32-lead ceramic soj type ecj 1 32
MYXX28HC256 revision 1.4 - 02/13 22 256kb eeprom MYXX28HC256 ordering information table 12 - device numbering device number package type speed temperature MYXX28HC256cw cerdip -7 = 70ns it/xt -9 = 90ns -12 = 120ns -15 = 150ns MYXX28HC256eca- cerlcc -7 = 70ns it/xt -9 = 90ns -12 = 120ns -15 = 150ns MYXX28HC256f- cerfp -7 = 70ns it/xt -9 = 90ns -12 = 120ns -15 = 150ns MYXX28HC256p- cerpga -7 = 70ns it/xt -9 = 90ns -12 = 120ns -15 = 150ns MYXX28HC256ecj cersoj -7 = 70ns it/xt -9 = 90ns -12 = 120ns -15 = 150ns it = industrial temperature range -40c to +85c xt = extended temperature range -55c to +125c
MYXX28HC256 revision 1.4 - 02/13 23 256kb eeprom MYXX28HC256 document title 32k x 8 eeprom - 5 volt, byte alterable revision history revision # history release date status 1.3 initial release november 2012 preliminary 1.4 added ceramic soj package drawing and option changed status to released corrected part number corrected ? gure designations february 2013 released


▲Up To Search▲   

 
Price & Availability of MYXX28HC256

All Rights Reserved © IC-ON-LINE 2003 - 2022  

[Add Bookmark] [Contact Us] [Link exchange] [Privacy policy]
Mirror Sites :  [www.datasheet.hk]   [www.maxim4u.com]  [www.ic-on-line.cn] [www.ic-on-line.com] [www.ic-on-line.net] [www.alldatasheet.com.cn] [www.gdcy.com]  [www.gdcy.net]


 . . . . .
  We use cookies to deliver the best possible web experience and assist with our advertising efforts. By continuing to use this site, you consent to the use of cookies. For more information on cookies, please take a look at our Privacy Policy. X